prices.minute
Overview
Theprices.minute
table provides the most granular price data for tokens across multiple blockchains, with minute-level precision. This is the highest resolution price data available in the Dune platform.
Table Schema
Column | Type | Description |
---|---|---|
blockchain | varchar | Blockchain identifier (e.g., ‘ethereum’, ‘arbitrum’) |
contract_address | varbinary | Token contract address (fixed address for native tokens) |
symbol | varchar | Token symbol (e.g., ‘ETH’, ‘USDC’) |
timestamp | timestamp | Minute timestamp |
price | double | Token price in USD (volume-weighted average) |
decimals | int | Token decimals |
volume | double | Trading volume in USD (from price source) |
source | varchar | Data source (‘coinpaprika’ or ‘dex.trades’) |
Implementation Details
The minute prices are built through these steps:- Collect sparse price observations from different sources
- Fill missing minutes with the previous minute’s price (forward filling)
- Set an expiration time of 48h for forward filling to avoid stale data
Usage
This table is ideal for high-frequency analysis and examining short-term price movements. It’s particularly useful for studying price impacts of specific events or transactions with high temporal precision. Note: While the table provides minute-level granularity, the underlying data sources are aligned to 5-minute intervals for consistency and improved data quality.Latency and Update Frequency
Theprices.minute
table is updated hourly based on the upstream data pipeline. As a result, prices typically have a latency of approximately 1 hour from real-time.
Usage Examples
Here are some examples of how to use the prices tables.Get minute-by-minute ETH prices during a specific event:
Analyze price volatility within short time frames:
Data Quality Notes
- Due to its high granularity, queries on this table may be more resource-intensive
- Consider using
prices.hour
orprices.day
for longer time ranges if minute-level precision is not required - Native tokens (like ETH, BNB) are assigned fixed addresses for consistency
- Always use
contract_address
andblockchain
for precise token identification, never usesymbol
for joins or filters - Prices are calculated using volume-weighted averages for more accurate representation
- Quality Filtering: The system includes filtering mechanisms to reduce the impact of anomalous trades
- Data Limitations: While filtering helps improve data quality, users should always validate prices for critical applications